Procurement APIs
Update provided S&OP (sales and operation planning) process
| HTTP method | PUT |
| URI | https://api.rambase.net/procurement/sop-processes/{sopProcessId} |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {sopProcessId} |
S&OP (sales and operation planning) process identifier
Integer, minimum 100000 |
| Successful HTTP status code | 200 |
| API resource identifier | 3379, version 19 |
The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.
SOPProcess
This field is optional.
>Name
Name of S&OP (Sales and operation planning) process
Minimum value: 1
This field is optional.
>{String}</Name>Description
Description of S&OP (Sales and operations planning) process
This field is optional.
>{String}</Description>Granularity
Granularity used to present the different plans in the S&OP process. Week or month.
Applicable domain values can be found here
This field is optional.
>{String}</Granularity>Location
This field is optional.
>LocationId
Location identifier
Minimum value: 10000
This field is optional.
>{Integer}</LocationId>DemandForecast
This field is optional.
>SalesForecastSource
The source to use from the sales forecast
Applicable domain values can be found here
This field is optional.
>{Integer}</SalesForecastSource>IncludeSalesBacklog
If sales backlog is included, everything from the backlog is added to the demand forecast. Note that backlog from products sales forecasted by customers (through the sales forecast source), will not be included.
This field is optional.
>{Boolean}</IncludeSalesBacklog>SalesBacklogExclusion
This field will only have any effect if the “include sales backlog” option is set.
The default (Exclude nothing) is that sales backlog for the same customer and product that exist in the sales forecast will be excluded from the sales and operation planning. This field is used to fine tune what will be included or not from the sales backlog.
Applicable domain values can be found here
This field is optional.
>{Integer}</SalesBacklogExclusion>IncludeReOrderPointForPurchase
If products which are purchased have specified re-order point for the location used in the S&OP process, the re-order point will be added as a demand. This will then be included in the gross quantity of the purchase requirements. Note that this also includes products with product structures manufactured externally.
This field is optional.
>{Boolean}</IncludeReOrderPointForPurchase>IncludeReOrderPointForProduction
If products which are manufactured have specified re-order point quantity for the location used in the S&OP process, the re-order point quantity will be added as a demand. This will then be included in the gross quantity of the production requirements. Note that this does not includes products with product structures manufactured externally.
This field is optional.
>{Boolean}</IncludeReOrderPointForProduction>MinimumProbabilityPercent
Minimum probability in percentage to include from the sales forecast
Minimum value: 0
Maximum value: 100
This field is optional.
>{Decimal}</MinimumProbabilityPercent>MaximumProbabilityPercent
Maximum probability in percentage to include from the sales forecast
Minimum value: 0
Maximum value: 100
This field is optional.
>{Decimal}</MaximumProbabilityPercent>ProductionRequirements
This field is optional.
>TreatProductionWorkOrdersAsStock
By enabling this, existing, but not completed, production work orders will be treated as stock. Any production work orders can be used to net off production requirements. By not enabling this, you might end up with creating new production work orders instead off replanning already existing production work orders.
This field is optional.
>{Boolean}</TreatProductionWorkOrdersAsStock>PurchaseRequirements
This field is optional.
>TreatSupplierBacklogAsStock
By enabling this all purchase orders and purchase order responses will be treated as stock. Any purchase orders and purchase order responses confirmed in the future (ex. in two months) is available from today and can be used to net off purchase requirements. By not enabling this, you might end up with purchasing products that could instead be aquired by requesting change of delivery date on existing supplier backlog.
This field is optional.
>{Boolean}</TreatSupplierBacklogAsStock>RequireMaterialsFromAllProductionWorkOrders
By enabling this option, materials from ALL ongoing- and planned production work orders are included as gross purchase requirements. This means that you might get purchase requirements for materials belonging to production work orders not related to the production requirement plan.
If this option is disabled, only materials needed to fulfill the production requirements are included as gross purchase requirements. Note that even if this option is disabled you will still get purchase requirements for materials in ongoing- and planned production work orders consumed by (net off) the production requirements.
This field is optional.
>{Boolean}</RequireMaterialsFromAllProductionWorkOrders>PurchaseOrderSuggestions
This field is optional.
>RequestedDeliveryDay
Preferred day of delivery. Used to consolidate purchase order suggestions. Default is all days.
Applicable domain values can be found here
Minimum value: 0
Maximum value: 7
This field is optional.
>{Integer}</RequestedDeliveryDay>SOPProcess
This field is optional.
": {Name
Name of S&OP (Sales and operation planning) process
Minimum value: 1
This field is optional.
": "{String}",Description
Description of S&OP (Sales and operations planning) process
This field is optional.
": "{String}",Granularity
Granularity used to present the different plans in the S&OP process. Week or month.
Applicable domain values can be found here
This field is optional.
": "{String}",Location
This field is optional.
": {LocationId
Location identifier
Minimum value: 10000
This field is optional.
": "{Integer}"DemandForecast
This field is optional.
": {SalesForecastSource
The source to use from the sales forecast
Applicable domain values can be found here
This field is optional.
": "{Integer}",IncludeSalesBacklog
If sales backlog is included, everything from the backlog is added to the demand forecast. Note that backlog from products sales forecasted by customers (through the sales forecast source), will not be included.
This field is optional.
": "{Boolean}",SalesBacklogExclusion
This field will only have any effect if the “include sales backlog” option is set.
The default (Exclude nothing) is that sales backlog for the same customer and product that exist in the sales forecast will be excluded from the sales and operation planning. This field is used to fine tune what will be included or not from the sales backlog.
Applicable domain values can be found here
This field is optional.
": "{Integer}",IncludeReOrderPointForPurchase
If products which are purchased have specified re-order point for the location used in the S&OP process, the re-order point will be added as a demand. This will then be included in the gross quantity of the purchase requirements. Note that this also includes products with product structures manufactured externally.
This field is optional.
": "{Boolean}",IncludeReOrderPointForProduction
If products which are manufactured have specified re-order point quantity for the location used in the S&OP process, the re-order point quantity will be added as a demand. This will then be included in the gross quantity of the production requirements. Note that this does not includes products with product structures manufactured externally.
This field is optional.
": "{Boolean}",MinimumProbabilityPercent
Minimum probability in percentage to include from the sales forecast
Minimum value: 0
Maximum value: 100
This field is optional.
": "{Decimal}",MaximumProbabilityPercent
Maximum probability in percentage to include from the sales forecast
Minimum value: 0
Maximum value: 100
This field is optional.
": "{Decimal}"ProductionRequirements
This field is optional.
": {TreatProductionWorkOrdersAsStock
By enabling this, existing, but not completed, production work orders will be treated as stock. Any production work orders can be used to net off production requirements. By not enabling this, you might end up with creating new production work orders instead off replanning already existing production work orders.
This field is optional.
": "{Boolean}"PurchaseRequirements
This field is optional.
": {TreatSupplierBacklogAsStock
By enabling this all purchase orders and purchase order responses will be treated as stock. Any purchase orders and purchase order responses confirmed in the future (ex. in two months) is available from today and can be used to net off purchase requirements. By not enabling this, you might end up with purchasing products that could instead be aquired by requesting change of delivery date on existing supplier backlog.
This field is optional.
": "{Boolean}",RequireMaterialsFromAllProductionWorkOrders
By enabling this option, materials from ALL ongoing- and planned production work orders are included as gross purchase requirements. This means that you might get purchase requirements for materials belonging to production work orders not related to the production requirement plan.
If this option is disabled, only materials needed to fulfill the production requirements are included as gross purchase requirements. Note that even if this option is disabled you will still get purchase requirements for materials in ongoing- and planned production work orders consumed by (net off) the production requirements.
This field is optional.
": "{Boolean}"PurchaseOrderSuggestions
This field is optional.
": {RequestedDeliveryDay
Preferred day of delivery. Used to consolidate purchase order suggestions. Default is all days.
Applicable domain values can be found here
Minimum value: 0
Maximum value: 7
This field is optional.
": "{Integer}"The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.
| $access_token String, optional | After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time. |
| $db String, optional | Set the database/company for the request |
| $useMinimumVersion Integer, optional | Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information. |
Read more about filters and sorting on how to use filter parameters and named filters.
Read more about filters and sorting on how to use sortable parameters
Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.
Please note that some fields may be removed from the response, based on user roles/duties/permissions.
List of available operations/actions for this resource.
See the operations documentation for more information about API operations.
Possible error codes the response might return:
| Error 104151 HTTP 400 | Name is required |